Remove the test data:

dotnet-docker/tests/Microsoft.DotNet.Docker.Tests/TestData.cs

Lines 350 to 351 in d7c2d2c

	new ProductImageData { Version = V8_0, VersionFamily = V8_0, OS = OS.AzureLinux30Distroless, OSTag = OS.MarinerDistroless, Arch = Arch.Amd64, SupportedImageRepos = DotNetImageRepo.Monitor },
	new ProductImageData { Version = V8_0, VersionFamily = V8_0, OS = OS.AzureLinux30Distroless, OSTag = OS.MarinerDistroless, Arch = Arch.Arm64, SupportedImageRepos = DotNetImageRepo.Monitor },

Also why isn't this failing? 😕 There might be an issue with monitor tests running:

I agree that the .NET Monitor test data needs to be removed (oops!), but this isn't indicative of the .NET Monitor tests not running. The tests are filtered using file paths to Dockerfiles based on the manifest. If the manifest doesn't have entries for the .NET Monitor 8.0 paths, then the .NET Monitor 8.0 image data is filtered out so they aren't run.

As for why Azure DevOps is saying they aren't executed (if you hover on the icon it has a tooltip of "Not executed"), I'm not sure. Here are the same visualizations for .NET 10 Azure Linux (which there aren't any .NET Monitor images yet):

and .NET 10 Windows Nano Server (where .NET Monitor has never had any Windows images):

So in my mind, it showing "Not executed" for some test doesn't really mean anything.

In any event, I will remove the .NET Monitor 8.0 image test data.

The tests are filtered using file paths to Dockerfiles based on the manifest. If the manifest doesn't have entries for the .NET Monitor 8.0 paths, then the .NET Monitor 8.0 image data is filtered out so they aren't run.

Ah, yeah, makes sense with the current setup. No concern from me then.